Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

docs: mention PSS in changeover procedure and replace Replicated Security with Interchain Security #1981

Merged
merged 3 commits into from
Jun 24, 2024

Conversation

insumity
Copy link
Contributor

@insumity insumity commented Jun 21, 2024

Description

Closes: #1971

Note that not all "replicated security" references were changed to "interchain security" when "replicated security" is used to refer to the specific protocol. For example, in the PSS ADR we refer to what the replicated security protocol was doing and hence it doesn't make sense to replace "replicated security" with "interchain security."


Author Checklist

All items are required. Please add a note to the item if the item is not applicable and
please add links to any relevant follow up issues.

I have...

  • included the correct docs: prefix in the PR title
  • targeted the correct branch (see PR Targeting)
  • provided a link to the relevant issue or specification
  • reviewed "Files changed" and left comments if necessary
  • confirmed all CI checks have passed

Reviewers Checklist

All items are required. Please add a note if the item is not applicable and please add
your handle next to the items reviewed if you only reviewed selected items.

I have...

  • Confirmed the correct docs: prefix in the PR title
  • Confirmed all author checklist items have been addressed
  • Confirmed that this PR only changes documentation
  • Reviewed content for consistency
  • Reviewed content for spelling and grammar
  • Tested instructions (if applicable)
  • Checked that the documentation website can be built and deployed successfully (run make build-docs)

Summary by CodeRabbit

  • Documentation
    • Updated terminology from "Replicated Security" to "Interchain Security" across various documents.
    • Clarified validator set sharing between provider and consumer chains.
    • Refined changeover procedures for transitioning standalone chains to Interchain Security.
    • Updated reward distribution documentation to reflect new security terms.
    • Improved clarity on validator requirements and node setup for Interchain Security.

@github-actions github-actions bot added C:Docs Assigned automatically by the PR labeler C:ADR Assigned automatically by the PR labeler labels Jun 21, 2024
@insumity insumity self-assigned this Jun 21, 2024
@insumity insumity marked this pull request as ready for review June 21, 2024 13:20
@insumity insumity requested a review from a team as a code owner June 21, 2024 13:20
Copy link
Contributor

coderabbitai bot commented Jun 21, 2024

Walkthrough

Walkthrough

The updates involve refining the behavior of consumer and provider chains within Interchain Security, replacing old terminology like "Replicated Security" with "Interchain Security." Key changes include clarifications in slashing, jailing, validator set sharing, changeover procedures, staking principles, reward distribution, and various semantic adjustments to the documentation.

Changes

Files Change Summary
...adr-005-cryptographic-equivocation-verification.md Clarified validator punishment logic for light client attacks. Updated assumptions about validator set sharing between chains.
...adr-008-throttle-retries.md Updated terminology from "slash throttling" to "jail throttling."
...adr-010-standalone-changeover.md Refined transition process for consumer chains integrating with Interchain Security.
.../consumer-development/app-integration.md Clarified staking logic using a subset of provider validators. Introduced Partial Set Security.
.../consumer-development/changeover-procedure.md Updates and clarifications for changeover procedures to Interchain Security.
...features/reward-distribution.md Semantic update from "Replicated Security" to "Interchain Security" in reward distribution mechanism documentation.
...frequently-asked-questions.md Updated link text to reflect Interchain Security terminology.
.../index.mdx Document updates to reflect Interchain Security terminology.
.../introduction/terminology.md Replaced "replicated security" with "Interchain Security" to clarify validator set distinctions.
.../validators/changeover-procedure.md Semantic changes related to transitioning to Interchain Security for validators.
.../validators/overview.md Updated terminology and clarified validator requirements and validation processes. Added references and queries related to validator obligations.
.../validators/withdraw_rewards.md Updated reference to testnet reflecting Interchain Security terminology.

Assessment against linked issues

Objective Addressed Explanation
Revise the Changeover Procedure section to reflect updates relevant to PSS (Partial Set Security) consumer chains and TopN if necessary. (#1971)
Replace "Replicated Security" with "Interchain Security." (#1971)

These changes meet the linked issues' requirements of updating and refining procedures and terminology to better reflect the current workings of Interchain Security.


Recent review details

Configuration used: .coderabbit.yml
Review profile: CHILL

Commits

Files that changed from the base of the PR and between 060c943 and b56650a.

Files selected for processing (12)
  • docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md (1 hunks)
  • docs/docs/adrs/adr-008-throttle-retries.md (1 hunks)
  • docs/docs/adrs/adr-010-standalone-changeover.md (2 hunks)
  • docs/docs/consumer-development/app-integration.md (1 hunks)
  • docs/docs/consumer-development/changeover-procedure.md (4 hunks)
  • docs/docs/features/reward-distribution.md (1 hunks)
  • docs/docs/frequently-asked-questions.md (1 hunks)
  • docs/docs/index.mdx (1 hunks)
  • docs/docs/introduction/terminology.md (1 hunks)
  • docs/docs/validators/changeover-procedure.md (1 hunks)
  • docs/docs/validators/overview.md (1 hunks)
  • docs/docs/validators/withdraw_rewards.md (1 hunks)
Files not reviewed due to errors (1)
  • docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md (no review received)
Files skipped from review due to trivial changes (1)
  • docs/docs/index.mdx
Additional context used
Path-based instructions (11)
docs/docs/validators/withdraw_rewards.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness. Please DO NOT report any missing or superfluous newlines, in particular at the end or beginning of files."

docs/docs/consumer-development/app-integration.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness. Please DO NOT report any missing or superfluous newlines, in particular at the end or beginning of files."

docs/docs/features/reward-distribution.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness. Please DO NOT report any missing or superfluous newlines, in particular at the end or beginning of files."

docs/docs/introduction/terminology.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness. Please DO NOT report any missing or superfluous newlines, in particular at the end or beginning of files."

docs/docs/adrs/adr-010-standalone-changeover.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness. Please DO NOT report any missing or superfluous newlines, in particular at the end or beginning of files."

docs/docs/validators/changeover-procedure.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness. Please DO NOT report any missing or superfluous newlines, in particular at the end or beginning of files."

docs/docs/validators/overview.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness. Please DO NOT report any missing or superfluous newlines, in particular at the end or beginning of files."

docs/docs/frequently-asked-questions.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness. Please DO NOT report any missing or superfluous newlines, in particular at the end or beginning of files."

docs/docs/adrs/adr-008-throttle-retries.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness. Please DO NOT report any missing or superfluous newlines, in particular at the end or beginning of files."

docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness. Please DO NOT report any missing or superfluous newlines, in particular at the end or beginning of files."

docs/docs/consumer-development/changeover-procedure.md (1)

Pattern **/*.md: "Assess the documentation for misspellings, grammatical errors, missing documentation and correctness. Please DO NOT report any missing or superfluous newlines, in particular at the end or beginning of files."

LanguageTool
docs/docs/validators/withdraw_rewards.md

[style] ~24-~24: ‘Prior to’ might be wordy. Consider a shorter alternative. (EN_WORDINESS_PREMIUM_PRIOR_TO)
Context: ...c8l6g4808fclmlyd38tjgxuwshn7xzkvf` ::: Prior to withdrawing rewards, query balances for...


[uncategorized] ~64-~64: A comma might be missing here. (AI_EN_LECTOR_MISSING_PUNCTUATION_COMMA)
Context: ...2. Confirm withdrawal After withdrawing rewards self-delegation address balance to conf...

docs/docs/consumer-development/app-integration.md

[uncategorized] ~6-~6: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ..., besides just focusing on your chain's logic you should aim to allocate time to ensu...


[uncategorized] ~25-~25: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...bution, x/stakingandx/governance` modules allowing the consumer chain to perform ...

docs/docs/features/reward-distribution.md

[misspelling] ~40-~40: This word is normally spelled with a hyphen. (EN_COMPOUNDS_HUMAN_READABLE)
Context: ...:tip Use the following command to get a human readable denom from the ibc/* denom trace form...

docs/docs/introduction/terminology.md

[uncategorized] ~11-~11: The abbreviation “i.e.” (= that is) requires two periods. (I_E)
Context: ...lups, sharding and Interchain Security. Ie. any protocol or technology that can all...

docs/docs/adrs/adr-010-standalone-changeover.md

[style] ~22-~22: ‘Prior to’ might be wordy. Consider a shorter alternative. (EN_WORDINESS_PREMIUM_PRIOR_TO)
Context: ...ver process. ## Decision ### Process Prior to the changeover, the consumer chain will...


[uncategorized] ~25-~25: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...er for validators to query. Within this consumer genesis contains the initial validator ...


[grammar] ~27-~27: Make sure that the noun ‘setup’ is correct. Did you mean the past participle “set up”? (BE_VB_OR_NN)
Context: ...ch adds the CCV module, and is properly setup to execute changeover logic. The consu...


[uncategorized] ~39-~39: The abbreviation “i.e.” (= that is) requires two periods. (I_E)
Context: ...ed before the changeover was completed. Ie. any infraction from a block height befo...


[style] ~45-~45: As a shorter alternative for ‘able to’, consider using “can now”. (BE_ABLE_TO)
Context: ... ### Positive * Existing cosmos chains are now able to onboard over to a consumer chain secure...


[uncategorized] ~50-~50: The abbreviation “i.e.” (= that is) requires two periods. (I_E)
Context: ...sumers in this repo becomes less clear. Ie. there is code in the [democracy consume...

docs/docs/validators/changeover-procedure.md

[misspelling] ~15-~15: Although “with regards to” is sometimes used in casual speech, it is typically considered a nonstandard phrase. (IN_OR_WITH_REGARDS_TO_OF)
Context: ...EVLj0WJcwt). There is some flexibility with regards to how the changeover procedure is execute...


[style] ~47-~47: Consider using a different verb to strengthen your wording. (MAKE_SURE_ENSURE)
Context: ...ration depends on your setup, so please make sure you prepare ahead of time. :::danger T...


[typographical] ~80-~80: It seems that a comma is missing. (IF_PLEASE_COMMA)
Context: ...y? Yes. If you are planning to do this please make sure that the node is synced with ...


[style] ~80-~80: Consider using a different verb to strengthen your wording. (MAKE_SURE_ENSURE)
Context: ... If you are planning to do this please make sure that the node is synced with `standalon...

docs/docs/validators/overview.md

[uncategorized] ~10-~10: The abbreviation “i.e.” (= that is) requires two periods. (I_E)
Context: ...l the validators of the provider chain (ie. Cosmos Hub) to run validator nodes for ...


[typographical] ~68-~68: Consider adding a comma here. (PLEASE_COMMA)
Context: ...start their consumer chain node. :::tip Please pay attention to any onboarding reposit...


[uncategorized] ~75-~75: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ... Finally, to fully establish interchain security an IBC relayer is used to establish con...


[uncategorized] ~99-~99: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...out equivocation handling in interchain security check out the [Slashing](../features/sl...


[uncategorized] ~104-~104: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...d on the provider before use. For more information check out the [Key assignment overview ...

docs/docs/frequently-asked-questions.md

[uncategorized] ~32-~32: Use a comma before ‘so’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE_2)
Context: ...or running them in separate environments so failure of one machine does not impact ...


[grammar] ~49-~49: The verb form ‘sends’ does not seem to match the subject ‘chains’. (SUBJECT_VERB_AGREEMENT_PLURAL)
Context: ...ators and stakers? The consumer chains sends a portion of its fees and inflation as ...


[formatting] ~58-~58: Consider inserting a comma after an introductory phrase for better readability. (IN_THAT_CASE_COMMA)
Context: ...ain have its own governance? Yes. In that case the validators are not necessarily part...


[uncategorized] ~61-~61: Use a comma before ‘but’ if it connects two independent clauses (unless they are closely connected and short). (COMMA_COMPOUND_SENTENCE_2)
Context: ... Validators can also be representatives but representatives are not required to run...


[uncategorized] ~90-~90: A comma may be missing after the conjunctive/linking adverb ‘Currently’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ....md) ## Which relayers are supported? Currently supported versions: - Hermes 1.8.0 ##...

docs/docs/adrs/adr-008-throttle-retries.md

[uncategorized] ~22-~22: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ing are synonymous, since in Interchain Security a SlashPacket simply jails a validato...


[uncategorized] ~23-~23: A comma may be missing after the conjunctive/linking adverb ‘Currently’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ... a validator for downtime infractions. Currently the throttling mechanism is designed so...


[uncategorized] ~28-~28: If this is a compound adjective that modifies the following noun, use a hyphen. (EN_COMPOUND_ADJECTIVE_INTERNAL)
Context: ...tially lead to a DoS attack. We have short term solutions around this, but overall they...


[uncategorized] ~28-~28: It seems that a comma is missing after the introductory phrase. (OVER_ALL_COMPOUND)
Context: ...e short term solutions around this, but overall they come with their own weaknesses. ...


[uncategorized] ~40-~40: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ed. ## Decision ### Consumer changes Note the consumer already queues up both `Sl...


[uncategorized] ~56-~56: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ... resending the rejected SlashPacket. Note to prevent weird edge case behavior, a ...


[misspelling] ~80-~80: Use “an” instead of ‘a’ if the following word starts with a vowel sound, e.g. ‘an article’, ‘an hour’. (EN_A_VS_AN)
Context: ...h sdk-esq code. The idea is to persist a uint64 index that will be incremented e...


[typographical] ~83-~83: The conjunction “so that” does not require a comma. (SO_THAT_UNNECESSARY_COMMA)
Context: ...be stored in the packet data value bytes, so that the index can later be used to delete c...


[grammar] ~87-~87: Context suggests that you should use the plural form of ‘packet’. (MORE_NN)
Context: ...d with this approach: * More efficient packet append/enqueue times * The ability to d...


[typographical] ~99-~99: Consider adding a comma after ‘Specifically’ for more clarity. (RB_LY_COMMA)
Context: ...erties.md#consumer-initiated-slashing). Specifically the section on _VSC Maturity and Slashi...


[uncategorized] ~99-~99: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...n on VSC Maturity and Slashing Order. Previously the onus was on the provider to maintai...


[uncategorized] ~99-~99: Possible missing preposition found. (AI_HYDRA_LEO_MISSING_IN)
Context: ...y via queuing packets and handling them FIFO. Now this property will be maintained ...


[uncategorized] ~142-~142: When ‘chain-specific’ is used as a modifier, it is usually spelled with a hyphen. (SPECIFIC_HYPHEN)
Context: ...to reason about a "global queue" and a "chain specific queue", and keeping those all in-sync. ...


[duplication] ~158-~158: Possible typo: you repeated a word (ENGLISH_WORD_REPEAT_RULE)
Context: ...) tracking the changes proposed by this ADR * [ADR 002: Jail Throttling](./adr-002-throttl...

docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md

[grammar] ~53-~53: ‘an’ may be redundant when used with the uncountable noun ‘evidence’. (A_UNCOUNTABLE_NOUN)
Context: ...blob/v0.34.28/evidence/pool.go#L28). If an evidence is finally committed to a block, the ch...

docs/docs/consumer-development/changeover-procedure.md

[style] ~45-~45: To form a complete sentence, be sure to include a subject. (MISSING_IT_THERE)
Context: ...visionHeight: 111 ::: * genesis_hash can be safely ignored because the chain is ...


[style] ~47-~47: To form a complete sentence, be sure to include a subject. (MISSING_IT_THERE)
Context: ...al genesis may be used * binary_hash may not be available ahead of time. All cha...


[typographical] ~98-~98: The word “otherwise” is an adverb that can’t be used like a conjunction, and therefore needs to be separated from the sentence. (THUS_SENTENCE)
Context: ...e must be placed at the exact specified location, otherwise the upgrade will not be executed correc...


[typographical] ~99-~99: Consider adding a comma after ‘Usually’ for more clarity. (RB_LY_COMMA)
Context: ...pgrade will not be executed correctly. Usually the file is placed in `$NODE_HOME/confi...


[typographical] ~239-~239: Usually, there’s no comma before “that”. (THAT_NO_COMMA)
Context: ...015-partial-set-security.md). This means, that a standalone chain can choose to only b...

Markdownlint
docs/docs/validators/withdraw_rewards.md

14-14: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


53-53: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


15-15: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


38-38: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


56-56: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


63-63: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


57-57: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines

docs/docs/consumer-development/app-integration.md

35-35: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines

docs/docs/features/reward-distribution.md

12-12: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


13-13: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


16-16: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


17-17: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


26-26: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


28-28: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


31-31: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


41-41: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


46-46: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


47-47: null (MD047, single-trailing-newline)
Files should end with a single newline character

docs/docs/validators/changeover-procedure.md

82-82: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


83-83: null (MD019, no-multiple-space-atx)
Multiple spaces after hash on atx style heading


91-91: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


25-25: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


66-66: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines

docs/docs/validators/overview.md

16-16: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


5-5: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


25-25: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


38-38: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


41-41: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


48-48: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


58-58: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


61-61: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


74-74: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


87-87: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


98-98: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


101-101: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


106-106: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


106-106: Punctuation: ':' (MD026, no-trailing-punctuation)
Trailing punctuation in heading


52-52: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


44-44: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


107-107: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines

docs/docs/frequently-asked-questions.md

136-136: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


114-114: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


117-117: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


120-120: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


123-123: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


126-126: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


129-129: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


133-133: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


136-136: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


137-137: null (MD047, single-trailing-newline)
Files should end with a single newline character

docs/docs/adrs/adr-008-throttle-retries.md

24-24: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


27-27: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


28-28: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


30-30: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


31-31: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


32-32: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


41-41: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


46-46: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


47-47: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


49-49: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


53-53: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


54-54: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


59-59: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


70-70: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


71-71: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


72-72: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


73-73: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


76-76: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


79-79: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


80-80: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


81-81: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


82-82: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


94-94: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


105-105: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


113-113: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


114-114: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


117-117: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


118-118: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


123-123: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


125-125: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


142-142: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


125-125: Expected: underscore; Actual: asterisk (MD049, emphasis-style)
Emphasis style


125-125: Expected: underscore; Actual: asterisk (MD049, emphasis-style)
Emphasis style

docs/docs/adrs/adr-005-cryptographic-equivocation-verification.md

126-126: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


134-134: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


137-137: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


141-141: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


148-148: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


153-153: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


19-19: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


20-20: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


30-30: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


44-44: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


64-64: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


65-65: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


66-66: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


67-67: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


70-70: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


71-71: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


72-72: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


73-73: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


74-74: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


75-75: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


78-78: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


79-79: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


98-98: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


103-103: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


104-104: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


107-107: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


108-108: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


109-109: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


110-110: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


111-111: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


112-112: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


114-114: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


116-116: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


117-117: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


119-119: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


120-120: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


134-134: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


138-138: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


139-139: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


148-148: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


55-55: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


82-82: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


123-123: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


143-143: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


155-155: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


7-7: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


5-5: null (MD025, single-title, single-h1)
Multiple top-level headings in the same document


124-124: Punctuation: ':' (MD026, no-trailing-punctuation)
Trailing punctuation in heading


8-8: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines

docs/docs/consumer-development/changeover-procedure.md

120-120: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


121-121: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


122-122: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


123-123: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


131-131: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


132-132: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


133-133: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


134-134: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


135-135: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


136-136: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


149-149: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


150-150: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


151-151: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


247-247: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


248-248: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


253-253: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


254-254: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


258-258: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


259-259: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


260-260: Expected: asterisk; Actual: dash (MD004, ul-style)
Unordered list style


209-209: Column: 1 (MD010, no-hard-tabs)
Hard tabs


210-210: Column: 1 (MD010, no-hard-tabs)
Hard tabs


211-211: Column: 1 (MD010, no-hard-tabs)
Hard tabs


74-74: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


250-250: Expected: 1; Actual: 2 (MD012, no-multiple-blanks)
Multiple consecutive blank lines


17-17: Expected: 1; Actual: 0; Below (MD022, blanks-around-headings)
Headings should be surrounded by blank lines


26-26: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


41-41: null (MD031, blanks-around-fences)
Fenced code blocks should be surrounded by blank lines


10-10: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


49-49: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


101-101: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


101-101: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines


26-26: null (MD040, fenced-code-language)
Fenced code blocks should have a language specified

Additional comments not posted (8)
docs/docs/validators/withdraw_rewards.md (1)

19-19: Update terminology to align with current project standards

The term "rs-testnet" has been updated to "Interchain Security persistent testnet" to reflect the current terminology used in the project. This change ensures consistency and helps avoid confusion.

docs/docs/consumer-development/app-integration.md (1)

13-15: Clarification on partial set security

The introduction of Partial Set Security (PSS) is correctly highlighted, indicating that not all provider validators need to validate a consumer chain. This is a crucial update for developers integrating with the ICS protocol, as it affects the scalability and flexibility of consumer chains.

docs/docs/features/reward-distribution.md (1)

11-11: Clarify reward distribution mechanism

The update clearly explains the mechanism of reward distribution from consumer chains to the provider chain using an IBC transfer channel. This is a significant detail that aligns with the updated protocol specifications.

docs/docs/introduction/terminology.md (1)

32-32: Clarification on Interchain Security's functionality

The description accurately explains how Interchain Security allows a subset of the provider chain's validator set to validate blocks on the consumer chain. This is an essential update for understanding the scope and functionality of the protocol.

docs/docs/validators/overview.md (1)

10-14: Clarification on validator requirements for consumer chains.

The explanation of the conditions under which a validator must run a validator node for a consumer chain is clear and well-detailed. The addition of the has-to-validate query provides a useful tool for validators to manage their responsibilities.

Tools
LanguageTool

[uncategorized] ~10-~10: The abbreviation “i.e.” (= that is) requires two periods. (I_E)
Context: ...l the validators of the provider chain (ie. Cosmos Hub) to run validator nodes for ...

docs/docs/frequently-asked-questions.md (1)

83-83: Updated link text for joining the testnet.

The update from "Joining Replicated Security testnet" to "Joining Interchain Security testnet" is accurate and reflects the terminology changes discussed in the PR. Good attention to detail.

docs/docs/consumer-development/changeover-procedure.md (2)

Line range hint 157-233: Review the ConsumerAdditionProposal Structure for Consistency and Clarity

This large block defines a ConsumerAdditionProposal. It's important to ensure that all fields are correctly explained and consistent with the rest of the documentation. Also, verify that the example values provided (like revision_number and upgrade_height) are realistic and align with typical usage scenarios.

Tools
LanguageTool

[typographical] ~239-~239: Usually, there’s no comma before “that”. (THAT_NO_COMMA)
Context: ...015-partial-set-security.md). This means, that a standalone chain can choose to only b...


93-93: Ensure Accuracy of Module Path

The documentation specifies adding the ccv/consumer module. It's crucial to verify that the path provided is accurate and reflects the actual module path used in the codebase.

Verification successful

Ensure Accuracy of Module Path

The ccv/consumer module path is correctly referenced in the documentation, as it aligns with the actual module path x/ccv/consumer in the codebase.

  • Verified Files:
    • x/ccv/consumer/module.go
    • x/ccv/consumer/types/validator.go
    • x/ccv/consumer/keeper/hooks.go
    • and many more within the x/ccv/consumer directory.
Scripts executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Searching for the module path in the codebase
rg --type md 'ccv/consumer' 

Length of output: 5744



Script:

#!/bin/bash
# Verify the existence of the x/ccv/consumer directory and list its contents
fd 'ccv/consumer' --type d --exec ls -l {}

Length of output: 44



Script:

#!/bin/bash
# Re-run the search for the ccv/consumer directory using rg to ensure comprehensive verification
rg --files | grep 'ccv/consumer'

Length of output: 1673


Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share
Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 9

Outside diff range and nitpick comments (17)
docs/docs/validators/withdraw_rewards.md (2)

Line range hint 24-24: Consider rephrasing for conciseness

The phrase "Prior to withdrawing rewards" could be simplified to "Before withdrawing rewards" for conciseness and improved readability.

- Prior to withdrawing rewards, query balances for self-delegation address:
+ Before withdrawing rewards, query balances for self-delegation address:

Line range hint 64-64: Add a comma for clarity

The sentence structure here could be improved by adding a comma after "After withdrawing rewards" to enhance readability and ensure grammatical correctness.

- After withdrawing rewards self-delegation address balance to confirm rewards were withdrawn:
+ After withdrawing rewards, check the self-delegation address balance to confirm rewards were withdrawn:
docs/docs/consumer-development/app-integration.md (2)

Line range hint 6-6: Add comma for better readability

Inserting a comma after "chain's logic" will improve the flow and readability of the sentence.

- When developing an ICS consumer chain, besides just focusing on your chain's logic you should aim to allocate time to ensure that your chain is compatible with the ICS protocol.
+ When developing an ICS consumer chain, besides just focusing on your chain's logic, you should aim to allocate time to ensure that your chain is compatible with the ICS protocol.

Line range hint 25-25: Add comma for grammatical correctness

A comma should be added after "x/staking" to separate the items in the list correctly.

- The source code for the example app can be found here, wrapping the basic CosmosSDK x/distribution, x/staking and x/governance modules allowing the consumer chain to perform democratic actions such as participating and voting within the chain's governance system.
+ The source code for the example app can be found here, wrapping the basic CosmosSDK x/distribution, x/staking, and x/governance modules allowing the consumer chain to perform democratic actions such as participating and voting within the chain's governance system.
docs/docs/features/reward-distribution.md (1)

Line range hint 40-40: Hyphenate 'human readable' for grammatical accuracy

The term "human readable" should be hyphenated when used as an adjective to improve the grammatical accuracy of the documentation.

- Use the following command to get a human readable denom from the `ibc/*` denom trace format:
+ Use the following command to get a human-readable denom from the `ibc/*` denom trace format:
Tools
Markdownlint

12-12: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


13-13: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces

docs/docs/introduction/terminology.md (1)

Line range hint 11-11: Correct abbreviation usage

The abbreviation "i.e." should be used instead of "Ie." to adhere to standard English conventions.

- Shared security is a family of technologies that include optimistic rollups, zk-rollups, sharding and Interchain Security. Ie. any protocol or technology that can allow one blockchain to lend/share its proof-of-stake security with another blockchain or off-chain process.
+ Shared security is a family of technologies that include optimistic rollups, zk-rollups, sharding and Interchain Security, i.e., any protocol or technology that can allow one blockchain to lend/share its proof-of-stake security with another blockchain or off-chain process.
docs/docs/adrs/adr-010-standalone-changeover.md (2)

Line range hint 39-39: Grammatical correction for abbreviation usage.

The abbreviation "i.e." should have two periods. Consider revising for grammatical accuracy.

- Ie. any infraction from a block height before the changeover, that is submitted after the changeover, will call the standalone staking keeper's slash method.
+ i.e., any infraction from a block height before the changeover that is submitted after the changeover will call the standalone staking keeper's slash method.

Line range hint 45-45: Enhance clarity with a more direct phrase.

The phrase "are now able to onboard over to" could be simplified for clarity and conciseness.

- Existing cosmos chains are now able to onboard over to a consumer chain secured by a provider.
+ Existing cosmos chains can now onboard to a consumer chain secured by a provider.
docs/docs/adrs/adr-008-throttle-retries.md (8)

Line range hint 28-28: Hyphenate compound adjectives for clarity.

The phrase "short term solutions" functions as a compound adjective and should be hyphenated to avoid ambiguity.

- We have short term solutions around this, but overall they come with their own weaknesses.
+ We have short-term solutions around this, but overall they come with their own weaknesses.
Tools
LanguageTool

[uncategorized] ~22-~22: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ing are synonymous, since in Interchain Security a SlashPacket simply jails a validato...


[uncategorized] ~23-~23: A comma may be missing after the conjunctive/linking adverb ‘Currently’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ... a validator for downtime infractions. Currently the throttling mechanism is designed so...

Markdownlint

24-24: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


Line range hint 40-40: Consider adding a comma for clarity.

In the sentence "Note the consumer already queues up both SlashPackets and VSCMaturedPackets via AppendPendingPacket," consider adding a comma after "Note" for better readability.

- Note the consumer already queues up both `SlashPackets` and `VSCMaturedPackets` via `AppendPendingPacket`.
+ Note, the consumer already queues up both `SlashPackets` and `VSCMaturedPackets` via `AppendPendingPacket`.
Tools
LanguageTool

[uncategorized] ~22-~22: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ing are synonymous, since in Interchain Security a SlashPacket simply jails a validato...


[uncategorized] ~23-~23: A comma may be missing after the conjunctive/linking adverb ‘Currently’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ... a validator for downtime infractions. Currently the throttling mechanism is designed so...

Markdownlint

24-24: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


Line range hint 56-56: Add a comma after 'Note' for clarity.

Adding a comma after "Note" in the sentence "Note to prevent weird edge case behavior, a retry would not be attempted until either a success or failure acknowledgement has been received from the provider" can improve the readability.

- Note to prevent weird edge case behavior, a retry would not be attempted until either a success or failure acknowledgement has been received from the provider.
+ Note, to prevent weird edge case behavior, a retry would not be attempted until either a success or failure acknowledgement has been received from the provider.
Tools
LanguageTool

[uncategorized] ~22-~22: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ing are synonymous, since in Interchain Security a SlashPacket simply jails a validato...


[uncategorized] ~23-~23: A comma may be missing after the conjunctive/linking adverb ‘Currently’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ... a validator for downtime infractions. Currently the throttling mechanism is designed so...

Markdownlint

24-24: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


Line range hint 80-80: Grammar correction for article usage.

The phrase "a uint64 index" should be "an uint64 index" since the following word starts with a vowel sound.

- The idea is to persist a uint64 index that will be incremented each time you queue up a packet.
+ The idea is to persist an uint64 index that will be incremented each time you queue up a packet.
Tools
LanguageTool

[uncategorized] ~22-~22: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ing are synonymous, since in Interchain Security a SlashPacket simply jails a validato...


[uncategorized] ~23-~23: A comma may be missing after the conjunctive/linking adverb ‘Currently’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ... a validator for downtime infractions. Currently the throttling mechanism is designed so...

Markdownlint

24-24: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


Line range hint 83-83: Remove unnecessary comma after 'so that'.

The sentence "The index will also be stored in the packet data value bytes, so that the index can later be used to delete certain packets from the queue" should not have a comma before "so that" as it introduces a necessary clause without pause.

- The index will also be stored in the packet data value bytes, so that the index can later be used to delete certain packets from the queue.
+ The index will also be stored in the packet data value bytes so that the index can later be used to delete certain packets from the queue.
Tools
LanguageTool

[uncategorized] ~22-~22: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ing are synonymous, since in Interchain Security a SlashPacket simply jails a validato...


[uncategorized] ~23-~23: A comma may be missing after the conjunctive/linking adverb ‘Currently’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ... a validator for downtime infractions. Currently the throttling mechanism is designed so...

Markdownlint

24-24: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


Line range hint 87-87: Grammar correction for plural form.

The word "packet" should be in its plural form "packets" to correctly refer to multiple items in the context.

- More efficient packet append/enqueue times
+ More efficient packets append/enqueue times
Tools
LanguageTool

[uncategorized] ~22-~22: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ing are synonymous, since in Interchain Security a SlashPacket simply jails a validato...


[uncategorized] ~23-~23: A comma may be missing after the conjunctive/linking adverb ‘Currently’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ... a validator for downtime infractions. Currently the throttling mechanism is designed so...

Markdownlint

24-24: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


Line range hint 99-99: Add a comma for clarity after introductory adverb.

Consider adding a comma after "Specifically" in the sentence "Specifically the section on VSC Maturity and Slashing Order" to improve readability.

- Specifically the section on _VSC Maturity and Slashing Order_.
+ Specifically, the section on _VSC Maturity and Slashing Order_.
Tools
LanguageTool

[uncategorized] ~22-~22: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ing are synonymous, since in Interchain Security a SlashPacket simply jails a validato...


[uncategorized] ~23-~23: A comma may be missing after the conjunctive/linking adverb ‘Currently’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ... a validator for downtime infractions. Currently the throttling mechanism is designed so...

Markdownlint

24-24: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces


Line range hint 142-142: Hyphenate 'chain-specific' when used as an adjective.

The phrase "chain specific queue" should be hyphenated to "chain-specific queue" to function correctly as a compound adjective.

- ...to reason about a "global queue" and a "chain specific queue", and keeping those all in-sync. ...
+ ...to reason about a "global queue" and a "chain-specific queue", and keeping those all in-sync. ...
Tools
LanguageTool

[uncategorized] ~22-~22: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ing are synonymous, since in Interchain Security a SlashPacket simply jails a validato...


[uncategorized] ~23-~23: A comma may be missing after the conjunctive/linking adverb ‘Currently’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ... a validator for downtime infractions. Currently the throttling mechanism is designed so...

Markdownlint

24-24: Expected: 0 or 2; Actual: 1 (MD009, no-trailing-spaces)
Trailing spaces

docs/docs/consumer-development/changeover-procedure.md (1)

Line range hint 98-98: Clarify Upgrade Execution Instructions

The sentence structure here is a bit complex. Consider rephrasing for clarity, especially the part about the exact location of the ConsumerGenesis file to ensure there's no ambiguity in upgrade execution instructions.

Tools
Markdownlint

10-10: null (MD032, blanks-around-lists)
Lists should be surrounded by blank lines

@@ -4,7 +4,7 @@ sidebar_position: 5

# Changeover Procedure

Chains that were not initially launched as consumers of replicated security can still participate in the protocol and leverage the economic security of the provider chain. The process where a standalone chain transitions to being a replicated consumer chain is called the **changeover procedure** and is part of the interchain security protocol. After the changeover, the new consumer chain will retain all existing state, including the IBC clients, connections and channels already established by the chain.
Chains that were **not** initially launched as consumers of Interchain Security can still participate in the protocol and leverage the economic security of the provider chain. The process where a standalone chain transitions to being a replicated consumer chain is called the **changeover procedure** and is part of the interchain security protocol. After the changeover, the new consumer chain will retain all existing state, including the IBC clients, connections and channels already established by the chain.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarify Terminology Consistency

The phrase "replicated consumer chain" is used, which seems inconsistent with the PR's objective to replace "Replicated Security" with "Interchain Security." Please ensure terminology is consistent throughout the document to avoid confusion.

Comment on lines +238 to +241
As seen in the `ConsumerAdditionProposal` example above, the changeover procedure can be used together with [Partial Set Security](../adrs/adr-015-partial-set-security.md).
This means, that a standalone chain can choose to only be validated by some of the validators of the provider chain by setting `top_N` appropriately, or by
additionally setting a validators-power cap, validator-set cap, etc. by using the [power-shaping parameters](../features/power-shaping.md).
:::
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarify Use of Power-Shaping Parameters

The section mentions using power-shaping parameters to limit validator participation. It's a complex concept that might require a more detailed explanation or a dedicated section to help readers understand the implications and usage.

Tools
LanguageTool

[typographical] ~239-~239: Usually, there’s no comma before “that”. (THAT_NO_COMMA)
Context: ...015-partial-set-security.md). This means, that a standalone chain can choose to only b...

@@ -19,7 +19,7 @@ Accepted

For context on why the throttling mechanism exists, see [ADR 002](./adr-002-throttle.md).

Note the terms slash throttling and jail throttling are synonymous, since in replicated security a `SlashPacket` simply jails a validator for downtime infractions.
Note the terms slash throttling and jail throttling are synonymous, since in Interchain Security a `SlashPacket` simply jails a validator for downtime infractions.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Add a comma after introductory adverb for clarity.

In the sentence starting with "Currently," it is stylistically better to add a comma after "Currently" to clearly delineate the introductory phrase from the main clause.

- Currently the throttling mechanism is designed so that provider logic (slash meter, etc.) dictates how many `SlashPackets` can be handled over time.
+ Currently, the throttling mechanism is designed so that provider logic (slash meter, etc.) dictates how many `SlashPackets` can be handled over time.
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Currently, the throttling mechanism is designed so that provider logic (slash meter, etc.) dictates how many `SlashPackets` can be handled over time.
Tools
LanguageTool

[uncategorized] ~23-~23: A comma may be missing after the conjunctive/linking adverb ‘Currently’. (SENT_START_CONJUNCTIVE_LINKING_ADVERB_COMMA)
Context: ... a validator for downtime infractions. Currently the throttling mechanism is designed so...

@@ -19,7 +19,7 @@

For context on why the throttling mechanism exists, see [ADR 002](./adr-002-throttle.md).

Note the terms slash throttling and jail throttling are synonymous, since in replicated security a `SlashPacket` simply jails a validator for downtime infractions.
Note the terms slash throttling and jail throttling are synonymous, since in Interchain Security a `SlashPacket` simply jails a validator for downtime infractions.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider adding a comma for clarity.

In the sentence "Note the terms slash throttling and jail throttling are synonymous, since in Interchain Security a SlashPacket simply jails a validator for downtime infractions," consider adding a comma after "synonymous" for better readability.

- Note the terms slash throttling and jail throttling are synonymous, since in Interchain Security a `SlashPacket` simply jails a validator for downtime infractions.
+ Note the terms slash throttling and jail throttling are synonymous, since in Interchain Security, a `SlashPacket` simply jails a validator for downtime infractions.
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
Note the terms slash throttling and jail throttling are synonymous, since in Interchain Security a `SlashPacket` simply jails a validator for downtime infractions.
Note the terms slash throttling and jail throttling are synonymous, since in Interchain Security, a `SlashPacket` simply jails a validator for downtime infractions.
Tools
LanguageTool

[uncategorized] ~22-~22: Possible missing comma found. (AI_HYDRA_LEO_MISSING_COMMA)
Context: ...ing are synonymous, since in Interchain Security a SlashPacket simply jails a validato...

@@ -14,7 +14,7 @@ Implemented

## Context

[Stride](https://github.com/Stride-Labs/stride) will be the first consumer to "changeover" from a standalone cosmos blockchain, to a consumer chain secured by the Cosmos Hub. This document will outline the changes made to the replicated security protocol to support this changeover process.
[Stride](https://github.com/Stride-Labs/stride) will be the first consumer to "changeover" from a standalone cosmos blockchain, to a consumer chain secured by the Cosmos Hub. This document outlines the changes made to support this changeover process.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Consider enhancing the introduction of Stride's role.

The introduction of Stride as the first consumer to changeover is crucial. It might be beneficial to expand slightly on why Stride was chosen or its significance in this context to provide a clearer picture to the readers.

@@ -26,7 +26,7 @@

Next, the standalone consumer chain runs an upgrade which adds the CCV module, and is properly setup to execute changeover logic.

The consumer upgrade height must be reached after the provider has created the new IBC client. Any replicated security validators who will run the consumer, but are not a part of the sovereign validator set, must sync up a full node before the consumer upgrade height is reached. The disk state of said full node will be used to run the consumer chain after the changeover has completed.
The consumer upgrade height must be reached after the provider has created the new IBC client. Any Interchain Security validators who will run the consumer, but are not a part of the sovereign validator set, must sync up a full node before the consumer upgrade height is reached. The disk state of said full node will be used to run the consumer chain after the changeover has completed.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarification needed on validator synchronization.

The sentence explaining the synchronization requirement for Interchain Security validators who are not part of the sovereign validator set is a bit complex. Consider rephrasing for clarity and ease of understanding.

- The consumer upgrade height must be reached after the provider has created the new IBC client. Any Interchain Security validators who will run the consumer, but are not a part of the sovereign validator set, must sync up a full node before the consumer upgrade height is reached.
+ Ensure that the consumer upgrade height is reached after the provider has created the new IBC client. Validators, not part of the sovereign set but responsible for running the consumer, must synchronize a full node before reaching the consumer upgrade height.
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
The consumer upgrade height must be reached after the provider has created the new IBC client. Any Interchain Security validators who will run the consumer, but are not a part of the sovereign validator set, must sync up a full node before the consumer upgrade height is reached. The disk state of said full node will be used to run the consumer chain after the changeover has completed.
The consumer upgrade height must be reached after the provider has created the new IBC client. Ensure that the consumer upgrade height is reached after the provider has created the new IBC client. Validators, not part of the sovereign set but responsible for running the consumer, must synchronize a full node before reaching the consumer upgrade height. The disk state of said full node will be used to run the consumer chain after the changeover has completed.

@@ -73,16 +73,16 @@ Yes.

Please assign your consensus key as stated above.

### Can I set up a new node to validate the `standalone/consumer` chain after it transitions to replicated security?
### Can I set up a new node to validate the `standalone/consumer` chain after it transitions to Interchain Security?
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarification on setting up new nodes post-transition.

The guidance on setting up new nodes after the transition to Interchain Security is clear, but it could be beneficial to include a note or link on the specific steps or considerations for syncing with the standalone network.

Would you like me to add detailed steps or a link to resources on syncing with the standalone network?

Comment on lines +83 to +85
### What happens to the `standalone` validator set after it transitions to Interchain Security?

The `standalone` chain validators will stop being validators after the first 3 blocks are created while using replicated security. The `standalone` validators will become **governors** and still can receive delegations if the `consumer` chain is using the `consumer-democracy` module.
The `standalone` chain validators will stop being validators after the first 3 blocks are created while using Interchain Security. The `standalone` validators will become **governors** and still can receive delegations if the `consumer` chain is using the `consumer-democracy` module.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Clarification on the role change for standalone validators.

The description of the transition of standalone validators to governors is clear. However, adding a brief explanation of what being a governor entails could enhance understanding for readers unfamiliar with the term.

- The standalone chain validators will stop being validators after the first 3 blocks are created while using Interchain Security. The standalone validators will become governors and still can receive delegations if the consumer chain is using the consumer-democracy module.
+ After the first 3 blocks post-transition to Interchain Security, standalone chain validators will cease to act as validators and will transition to governors. As governors, they can still receive delegations if the consumer chain utilizes the consumer-democracy module. Governors participate in governance but do not validate blocks.
Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
### What happens to the `standalone` validator set after it transitions to Interchain Security?
The `standalone` chain validators will stop being validators after the first 3 blocks are created while using replicated security. The `standalone` validators will become **governors** and still can receive delegations if the `consumer` chain is using the `consumer-democracy` module.
The `standalone` chain validators will stop being validators after the first 3 blocks are created while using Interchain Security. The `standalone` validators will become **governors** and still can receive delegations if the `consumer` chain is using the `consumer-democracy` module.
### What happens to the `standalone` validator set after it transitions to Interchain Security?
After the first 3 blocks post-transition to Interchain Security, standalone chain validators will cease to act as validators and will transition to governors. As governors, they can still receive delegations if the consumer chain utilizes the consumer-democracy module. Governors participate in governance but do not validate blocks.
Tools
Markdownlint

83-83: null (MD019, no-multiple-space-atx)
Multiple spaces after hash on atx style heading

Comment on lines +17 to +19
Once a `ConsumerAdditionProposal` passes, relevant validators need to prepare to run the consumer chain binaries (these will be linked in their proposals) and set up validator nodes on governance-approved consumer chains.

Provider chain and consumer chains represent standalone chains that only share part of the validator set.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Enhanced clarity on validator preparations.

The instructions for validators to prepare for running consumer chain binaries are clear. Consider linking directly to the proposals or providing examples to aid validators in finding the relevant binaries.

@insumity insumity added this pull request to the merge queue Jun 24, 2024
Merged via the queue into main with commit 590871b Jun 24, 2024
24 checks passed
@insumity insumity deleted the insumity/1971 branch June 24, 2024 08:55
mergify bot pushed a commit that referenced this pull request Jun 24, 2024
…rity with Interchain Security (#1981)

* removed sentence that stated that "no opt-in mechanism available"

* changed replicated security to interchain security

* added PSS info box in the changeover procedure

(cherry picked from commit 590871b)
mergify bot pushed a commit that referenced this pull request Jun 24, 2024
…rity with Interchain Security (#1981)

* removed sentence that stated that "no opt-in mechanism available"

* changed replicated security to interchain security

* added PSS info box in the changeover procedure

(cherry picked from commit 590871b)
MSalopek pushed a commit that referenced this pull request Jun 24, 2024
…rity with Interchain Security (backport #1981) (#1986)

docs: mention PSS in changeover procedure and replace Replicated Security with Interchain Security (#1981)

* removed sentence that stated that "no opt-in mechanism available"

* changed replicated security to interchain security

* added PSS info box in the changeover procedure

(cherry picked from commit 590871b)

Co-authored-by: insumity <[email protected]>
MSalopek pushed a commit that referenced this pull request Jun 24, 2024
…rity with Interchain Security (backport #1981) (#1985)

docs: mention PSS in changeover procedure and replace Replicated Security with Interchain Security (#1981)

* removed sentence that stated that "no opt-in mechanism available"

* changed replicated security to interchain security

* added PSS info box in the changeover procedure

(cherry picked from commit 590871b)

Co-authored-by: insumity <[email protected]>
sainoe added a commit that referenced this pull request Jul 16, 2024
* build(deps): bump slackapi/slack-github-action from 1.25.0 to 1.26.0 (#1803)

Bumps [slackapi/slack-github-action](https://github.com/slackapi/slack-github-action) from 1.25.0 to 1.26.0.
- [Release notes](https://github.com/slackapi/slack-github-action/releases)
- [Commits](https://github.com/slackapi/slack-github-action/compare/v1.25.0...v1.26.0)

---
updated-dependencies:
- dependency-name: slackapi/slack-github-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* chore: add v4.1.x to docs and cleanup bots (#1812)

* add v4.1.x to releases and features

* cleanup mergify and dependabot

* build(deps): bump github.com/cosmos/cosmos-proto from 1.0.0-beta.4 to 1.0.0-beta.5 (#1802)

build(deps): bump github.com/cosmos/cosmos-proto

Bumps [github.com/cosmos/cosmos-proto](https://github.com/cosmos/cosmos-proto) from 1.0.0-beta.4 to 1.0.0-beta.5.
- [Release notes](https://github.com/cosmos/cosmos-proto/releases)
- [Commits](https://github.com/cosmos/cosmos-proto/compare/v1.0.0-beta.4...v1.0.0-beta.5)

---
updated-dependencies:
- dependency-name: github.com/cosmos/cosmos-proto
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* docs: add docs versioning and legacy page (pre v4.0.0) (#1833)

* Updated build to allow for versioned docs

* wip: add steps to build legacy docs

* docs: add build legacy website

* docs: add v4; rename to legacy

* docs: add docs versioning for docusaurus v3.x

* docs: add docs version sync and deploy scripts

* update makefile

* docs: rm deprecated build script

* docs: fix banner in v4.1.0

* docs: update build script & config

* update .gitignore

* docs: update build script & config

* docs: update Readme

* build: update docs build script

* build: update docs README.md

* address review comments

* address review comments -- update readme

---------

Co-authored-by: Milan Mulji <[email protected]>

* build(deps): bump JamesIves/github-pages-deploy-action from 4.5.0 to 4.6.0 (#1804)

build(deps): bump JamesIves/github-pages-deploy-action

Bumps [JamesIves/github-pages-deploy-action](https://github.com/jamesives/github-pages-deploy-action) from 4.5.0 to 4.6.0.
- [Release notes](https://github.com/jamesives/github-pages-deploy-action/releases)
- [Commits](https://github.com/jamesives/github-pages-deploy-action/compare/v4.5.0...v4.6.0)

---
updated-dependencies:
- dependency-name: JamesIves/github-pages-deploy-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* chore: add release/v5.x bots targets (#1829)

* chore: fix spelling errors (#1835)

chore: spelling errors fixes

Co-authored-by: github-merge-queue <[email protected]>

* build(deps): bump github.com/hashicorp/go-getter from 1.7.1 to 1.7.4 (#1826)

Bumps [github.com/hashicorp/go-getter](https://github.com/hashicorp/go-getter) from 1.7.1 to 1.7.4.
- [Release notes](https://github.com/hashicorp/go-getter/releases)
- [Changelog](https://github.com/hashicorp/go-getter/blob/main/.goreleaser.yml)
- [Commits](https://github.com/hashicorp/go-getter/compare/v1.7.1...v1.7.4)

---
updated-dependencies:
- dependency-name: github.com/hashicorp/go-getter
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* docs: update docs deployment (#1841)

* build(deps): bump amannn/action-semantic-pull-request from 5.4.0 to 5.5.2 (#1831)

build(deps): bump amannn/action-semantic-pull-request

Bumps [amannn/action-semantic-pull-request](https://github.com/amannn/action-semantic-pull-request) from 5.4.0 to 5.5.2.
- [Release notes](https://github.com/amannn/action-semantic-pull-request/releases)
- [Changelog](https://github.com/amannn/action-semantic-pull-request/blob/main/CHANGELOG.md)
- [Commits](https://github.com/amannn/action-semantic-pull-request/compare/v5.4.0...v5.5.2)

---
updated-dependencies:
- dependency-name: amannn/action-semantic-pull-request
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump bufbuild/buf-setup-action from 1.30.1 to 1.31.0 (#1832)

Bumps [bufbuild/buf-setup-action](https://github.com/bufbuild/buf-setup-action) from 1.30.1 to 1.31.0.
- [Release notes](https://github.com/bufbuild/buf-setup-action/releases)
- [Commits](https://github.com/bufbuild/buf-setup-action/compare/v1.30.1...v1.31.0)

---
updated-dependencies:
- dependency-name: bufbuild/buf-setup-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* feat!: Introduce Partial Set Security (#1809)

* cleanup ./changelog entries

* docs: changelog and release notes for v4.0.0 (#1564)

* add v4.0.0 section to changelog

* add release notes

* fix!: Validation of SlashAcks fails due to marshaling to Bech32  (backport #1570) (#1577)

fix!: Validation of SlashAcks fails due to marshaling to Bech32  (#1570)

* add different Bech32Prefix for consumer and provider

* separate app encoding and params

* remove ConsumerValPubKey from ValidatorConfig

* update addresses in tests

* make SlashAcks consistent across chains

* add comments for clarity

* Regenerate traces

* Fix argument order

* set bech32prefix for provider to cosmos

* add changelog entries

* add consumer-double-downtime e2e test

* update nightly-e2e workflow

* fix typo

* add consumer-double-downtime to testConfigs

* remove changes on provider

* skip invalid SlashAcks

* seal the config

* clear the outstanding downtime flag for new vals

* add info on upgrading to v4.0.0

* fix upgrade handler

* fix changeover e2e test

* Update tests/e2e/config.go

Co-authored-by: Philip Offtermatt <[email protected]>

* Update tests/e2e/config.go

Co-authored-by: Philip Offtermatt <[email protected]>

* add AccountPrefix to ChainConfig

* fix docstrings

* update AccountAddressPrefix in app.go

* fix consumer-misb e2e test

---------

Co-authored-by: Philip Offtermatt <[email protected]>
Co-authored-by: Simon Noetzlin <[email protected]>
Co-authored-by: Philip Offtermatt <[email protected]>
(cherry picked from commit 86046926502f7b0ba795bebcdd1fdc97ac776573)

Co-authored-by: Marius Poke <[email protected]>

* docs: update changelog for v4.0.0 (#1578)

update changelog

* docs: prepare for v4.0.0 (#1581)

* unclog build

* update release notes

* update release date

* feat!: enable Opt In and Top N chains through gov proposals (#1615)

* init commit

* added test

* fixed tests

* added changelog entry and comment

* Update x/ccv/provider/keeper/proposal_test.go

Co-authored-by: Philip Offtermatt <[email protected]>

* Update .changelog/unreleased/features/1587-enable-opt-in-chains-through-gov-proposals.md

Co-authored-by: Philip Offtermatt <[email protected]>

* Update proto/interchain_security/ccv/provider/v1/provider.proto

Co-authored-by: Philip Offtermatt <[email protected]>

* Update proto/interchain_security/ccv/provider/v1/provider.proto

Co-authored-by: Philip Offtermatt <[email protected]>

* Update proto/interchain_security/ccv/provider/v1/provider.proto

Co-authored-by: Philip Offtermatt <[email protected]>

* Update proto/interchain_security/ccv/provider/v1/provider.proto

Co-authored-by: Philip Offtermatt <[email protected]>

* Update x/ccv/provider/keeper/keeper.go

Co-authored-by: Philip Offtermatt <[email protected]>

* changed to tabular test

---------

Co-authored-by: insumity <[email protected]>
Co-authored-by: Philip Offtermatt <[email protected]>

* feat!: introduce MsgOptIn and MsgOptOut (#1620)

* init commit

* cleaning up

* changed cons to val address

* Revert "changed cons to val address"

This reverts commit a32e8829fee3cbbe50e363a0aa91ad62117a8a1d.

* Update x/ccv/provider/keeper/keeper.go

Co-authored-by: Simon Noetzlin <[email protected]>

* took into account comments

* added key assignment

* add contraint such that opt out only works if the chain is running

---------

Co-authored-by: insumity <[email protected]>
Co-authored-by: Simon Noetzlin <[email protected]>

* test: MBT: Add partial set security to model (feature branch version) (#1627)

* Port changes from branch to main

* Add model analysis changes to Makefile

* test: Ports key assignment to the driver on the PSS feature branch (#1628)

* Port key assignment to MBT driver

* Add comment and make var names clearer

* feat!: automatically opt in validators that vote Yes on consumer addition proposals (#1629)

* init commit

* changed providerKeeper.GetProposedConsumerChain to return a  bool

* add logging mesages

* one more log message

* fix comment

* added one more test case of NO vote and made tabular test

* test: Add driver for PSS (#1636)

* Port key assignment to MBT driver

* Add PSS trace generation

* Add PSS trace gen to longer trace gen

* Start handling top N parameter for new consumers

* Finish merge

* Add handling for optin/optout steps

* Remove expected error from OptIn, which should not error

* set top N parameter during path setup

* Add comment to setup.go

* feat!: add PSS reward distribution spike (#1632)

* PSS reward distribution

* "add optin mapping to test"

* Update app/provider/app.go

Co-authored-by: Philip Offtermatt <[email protected]>

* docs

* add TODO

* fix Dos vector in IBCMiddlewarea

* add reformat

* fix DOS issue and make integration tests pass

* doc

* add integration test

* doc

* Compute total vp per consumer

* add comments

* remove opt-in comments and add TODOs

* format

* Update x/ccv/provider/keeper/distribution.go

Co-authored-by: insumity <[email protected]>

* add UT + doc

* Update tests/integration/distribution.go

Co-authored-by: insumity <[email protected]>

* Update tests/integration/distribution.go

Co-authored-by: insumity <[email protected]>

* nits

* Update x/ccv/provider/ibc_middleware.go

Co-authored-by: Marius Poke <[email protected]>

* add panics in IBC Middleware ICS4wrapper funcs

* address comments

---------

Co-authored-by: Philip Offtermatt <[email protected]>
Co-authored-by: insumity <[email protected]>
Co-authored-by: Marius Poke <[email protected]>

* feat! use protos to serialize opted-in validators (#1659)

move OptedInValidators to proto

Co-authored-by: insumity <[email protected]>

* feat!: PSS enable per-consumer chain commission (#1657)

* add draft commission

* implement consumer commission draft

* formatting

* add msg handling

* improve UT

* nits

* Update x/ccv/provider/keeper/keeper.go

Co-authored-by: insumity <[email protected]>

* Update proto/interchain_security/ccv/provider/v1/tx.proto

Co-authored-by: Marius Poke <[email protected]>

* optimize keys

* Update x/ccv/provider/keeper/keeper.go

Co-authored-by: insumity <[email protected]>

* address comments

* address comments

* remove unnecessary check

* Revert "remove unnecessary check"

This reverts commit 2951e9bace04f6436d6ad1e4a11efcedd0be8cb1.

* fix minor bug in StopConsumerChain

---------

Co-authored-by: insumity <[email protected]>
Co-authored-by: Marius Poke <[email protected]>

* test: update integration test suite for PSS (#1687)

* draft multi consumer transfer setup and test

* format multi consumer distribution test

* update test for democ consumer chains

* nits

* nit

* docs: changelog and release notes for v4.0.0 (#1564)

* add v4.0.0 section to changelog

* add release notes

* fix!: Validation of SlashAcks fails due to marshaling to Bech32  (backport #1570) (#1577)

fix!: Validation of SlashAcks fails due to marshaling to Bech32  (#1570)

* add different Bech32Prefix for consumer and provider

* separate app encoding and params

* remove ConsumerValPubKey from ValidatorConfig

* update addresses in tests

* make SlashAcks consistent across chains

* add comments for clarity

* Regenerate traces

* Fix argument order

* set bech32prefix for provider to cosmos

* add changelog entries

* add consumer-double-downtime e2e test

* update nightly-e2e workflow

* fix typo

* add consumer-double-downtime to testConfigs

* remove changes on provider

* skip invalid SlashAcks

* seal the config

* clear the outstanding downtime flag for new vals

* add info on upgrading to v4.0.0

* fix upgrade handler

* fix changeover e2e test

* Update tests/e2e/config.go

Co-authored-by: Philip Offtermatt <[email protected]>

* Update tests/e2e/config.go

Co-authored-by: Philip Offtermatt <[email protected]>

* add AccountPrefix to ChainConfig

* fix docstrings

* update AccountAddressPrefix in app.go

* fix consumer-misb e2e test

---------

Co-authored-by: Philip Offtermatt <[email protected]>
Co-authored-by: Simon Noetzlin <[email protected]>
Co-authored-by: Philip Offtermatt <[email protected]>
(cherry picked from commit 86046926502f7b0ba795bebcdd1fdc97ac776573)

Co-authored-by: Marius Poke <[email protected]>

* docs: update changelog for v4.0.0 (#1578)

update changelog

* feat!: enable Opt In and Top N chains through gov proposals (#1615)

* init commit

* added test

* fixed tests

* added changelog entry and comment

* Update x/ccv/provider/keeper/proposal_test.go

Co-authored-by: Philip Offtermatt <[email protected]>

* Update .changelog/unreleased/features/1587-enable-opt-in-chains-through-gov-proposals.md

Co-authored-by: Philip Offtermatt <[email protected]>

* Update proto/interchain_security/ccv/provider/v1/provider.proto

Co-authored-by: Philip Offtermatt <[email protected]>

* Update proto/interchain_security/ccv/provider/v1/provider.proto

Co-authored-by: Philip Offtermatt <[email protected]>

* Update proto/interchain_security/ccv/provider/v1/provider.proto

Co-authored-by: Philip Offtermatt <[email protected]>

* Update proto/interchain_security/ccv/provider/v1/provider.proto

Co-authored-by: Philip Offtermatt <[email protected]>

* Update x/ccv/provider/keeper/keeper.go

Co-authored-by: Philip Offtermatt <[email protected]>

* changed to tabular test

---------

Co-authored-by: insumity <[email protected]>
Co-authored-by: Philip Offtermatt <[email protected]>

* feat!: introduce MsgOptIn and MsgOptOut (#1620)

* init commit

* cleaning up

* changed cons to val address

* Revert "changed cons to val address"

This reverts commit a32e8829fee3cbbe50e363a0aa91ad62117a8a1d.

* Update x/ccv/provider/keeper/keeper.go

Co-authored-by: Simon Noetzlin <[email protected]>

* took into account comments

* added key assignment

* add contraint such that opt out only works if the chain is running

---------

Co-authored-by: insumity <[email protected]>
Co-authored-by: Simon Noetzlin <[email protected]>

* test: MBT: Add partial set security to model (feature branch version) (#1627)

* Port changes from branch to main

* Add model analysis changes to Makefile

* feat!: add PSS reward distribution spike (#1632)

* PSS reward distribution

* "add optin mapping to test"

* Update app/provider/app.go

Co-authored-by: Philip Offtermatt <[email protected]>

* docs

* add TODO

* fix Dos vector in IBCMiddlewarea

* add reformat

* fix DOS issue and make integration tests pass

* doc

* add integration test

* doc

* Compute total vp per consumer

* add comments

* remove opt-in comments and add TODOs

* format

* Update x/ccv/provider/keeper/distribution.go

Co-authored-by: insumity <[email protected]>

* add UT + doc

* Update tests/integration/distribution.go

Co-authored-by: insumity <[email protected]>

* Update tests/integration/distribution.go

Co-authored-by: insumity <[email protected]>

* nits

* Update x/ccv/provider/ibc_middleware.go

Co-authored-by: Marius Poke <[email protected]>

* add panics in IBC Middleware ICS4wrapper funcs

* address comments

---------

Co-authored-by: Philip Offtermatt <[email protected]>
Co-authored-by: insumity <[email protected]>
Co-authored-by: Marius Poke <[email protected]>

* feat!: PSS enable per-consumer chain commission (#1657)

* add draft commission

* implement consumer commission draft

* formatting

* add msg handling

* improve UT

* nits

* Update x/ccv/provider/keeper/keeper.go

Co-authored-by: insumity <[email protected]>

* Update proto/interchain_security/ccv/provider/v1/tx.proto

Co-authored-by: Marius Poke <[email protected]>

* optimize keys

* Update x/ccv/provider/keeper/keeper.go

Co-authored-by: insumity <[email protected]>

* address comments

* address comments

* remove unnecessary check

* Revert "remove unnecessary check"

This reverts commit 2951e9bace04f6436d6ad1e4a11efcedd0be8cb1.

* fix minor bug in StopConsumerChain

---------

Co-authored-by: insumity <[email protected]>
Co-authored-by: Marius Poke <[email protected]>

* fix nits in MBT model after merging #1676 from main

* Fix merging ccv model

* Remove conflict markers

* Remove more conflict markers

* EndProviderEpoch takes ConsumerAdditionMsg

* Fix using consumer addition msgs instead of chain names in boundeddrift.qnt

* lint

* chore: rebase PSS branch with main (#1689)

* Update tests/mbt/driver/mbt_test.go

* nits

* revert unwanted line deletion from linter

---------

Co-authored-by: Philip Offtermatt <[email protected]>

* feat!: complete the PSS reward distribution (#1709)

* update compute consumer total power for reward distribution

* update distribution logic to work with epochcs

* Adapt reward distribution mem test to epochs

* doc

* nits

* other nits

* nits

* Update tests/integration/distribution.go

* feat!: Add slashing logic for PSS (#1710)

* add check for consumer validators in downtime logic

* fix UT

* try to fix weird errors in gh worfklow

* fix silly merge bug

* nits

* ci: do not scan the tests for security issues (#1717)

init commit

* feat!: compute partial sets (#1702)

* init commit

* nit change

* cleaning up

* clean up

* fix distribution test

* Update x/ccv/provider/keeper/hooks.go

Co-authored-by: Simon Noetzlin <[email protected]>

* took into Simon's comments

* took into rest of the comments

* nit change

* return an error if validator cannot opt out from a Top N chain

* removed automatic opt-in for validators that vote Yes on proposals

* tiny fix for E2E tests

* nit change to remove unecessary else

* fixed topN == 0 issue

---------

Co-authored-by: Simon Noetzlin <[email protected]>

* feat!: update PSS cli (#1708)

finalize PSS CLI cmds

* Rename and add comission rate command to commands

* feat!: only perform consumer additions for non-empty chains (#1730)

* init commit

* Update x/ccv/provider/keeper/proposal.go

Co-authored-by: Philip Offtermatt <[email protected]>

---------

Co-authored-by: Philip Offtermatt <[email protected]>

* feat: Add queries for PSS and consumer commission rate (#1733)

* init commit

* nit change

* cleaning up

* clean up

* fix distribution test

* Update x/ccv/provider/keeper/hooks.go

Co-authored-by: Simon Noetzlin <[email protected]>

* took into Simon's comments

* took into rest of the comments

* nit change

* return an error if validator cannot opt out from a Top N chain

* removed automatic opt-in for validators that vote Yes on proposals

* tiny fix for E2E tests

* nit change to remove unecessary else

* update consumer chains query to return topN

* update query consu chains proto

* add consumer chains per validator query

* Add PSS command to provider's cli

* nits

* add consumer commission rate query

* nits

* big renaming

* fix doc

* nits

* nits

* docs

* Update proto/interchain_security/ccv/provider/v1/query.proto

Co-authored-by: insumity <[email protected]>

* nit

* add OptedIn in QueryConsumerChainsValidatorHasToValidate

* remove OptIn field in consumer chains query response

* include validators that opt-in during the next epochs

* update has-to-validate condition

* fix tinny bug in the tests after merging  feat/partial-security

* update doc

* update cli description

* Update x/ccv/provider/keeper/grpc_query.go

Co-authored-by: insumity <[email protected]>

* changes

---------

Co-authored-by: insumity <[email protected]>

* fix!: Fix opt-in assignment (#1732)

* Make the same validator assigning the same key a noop instead of an error

* Adjust test

* Update tests

* Fix newline warning

* Regenerate traces

* Add key assignment change to changelog

* Add info log for same key same validator assignments

* Add changelog entry to api-breaking

* Update x/ccv/provider/handler_test.go

Co-authored-by: insumity <[email protected]>

* Add more comments to test and return right validator

---------

Co-authored-by: insumity <[email protected]>

* fix silly bug in PSS opted-in val query

* fix logging in ibc_module.go

* test: add partial-set-security E2E tests (#1737)

* init commit

* fix traces

* Add PSS to default tests

* Update tests/e2e/steps_partial_set_security.go

Co-authored-by: Philip Offtermatt <[email protected]>

* Update tests/e2e/steps_partial_set_security.go

Co-authored-by: Philip Offtermatt <[email protected]>

---------

Co-authored-by: Philip Offtermatt <[email protected]>
Co-authored-by: Philip Offtermatt <[email protected]>

* Nit changes based on Simons comments. To be pushed directly because E2E PR 1737 were the comments were written was accidentally merged.

* fix!: return a SlashAck even if the validator is not a consumer validator (#1763)

* init commit

* fix test

* test: Expand PSS e2e test to include slashing (#1752)

* Expand test to include slashing

* Add back existing steps

* Add downtime to top N test

* Fix nits

* fix!: update unbonding  pausing for PSS (#1728)

* draft PSS unbonding fix

* fix hook logic to retrieve validator address from ubd op

* add unbonding pausing unit-test

* remove panic in hook

* Get back 3.2.0 and 3.3.0 changelog from main

* Port epilogue from main

* Fix proto conflict

* generate proto files

* Port RELEASE_NOTES

* Fix merge for tests

* Merge declaration and assignment

* Clean up model files

* Add pss tests to MBT readme

* Restore MsgSubmitConsumerDoubleVoting handler

* Remove local driver files

* Remove Quint guidelines

* Add optin/optout to MBT readme

* Fix types in model

* Fix model

* Add migration

* Ensure SlashAcks are sent even when the valset does not change

* adding changelog entry

* Empty DowntimeSlachAcks on EndBlock

* Remove logs

* Change condition for sending slash acks

* Revert model changes

* Start fixing PSS issues in model

* Add expected errors to opt out action

* Revert PSS quint model changes

* Add parameter to ComputeNextEpochConsumerValSet

* Set top N param in setup

* Fix: do not try key assignment if there is no nonjailed validator

* Do not assign keys for jailed validators

* Only jail validators with non-zero-power

* Add unit test

* Add unit test for unset case

* Panic on not being able to unmarshal

* Move packet handling into ack.Success block

* Format

* Remove unnecessary comment

* Add parens for clarity

* Format and fix typo

* Move OptIn/OptOut events to provider events

* Remove unused function

* Improve comments for keys

* Improve comments for key getter functions

* Remove order change for existing keys

* Re-add nolint instruction

* nit comment fix

* Move ConsumerAllocationTests to correct folder

* nit comment fix

* fix!: handle consumer commission marshalling errors gracefully (#1836)

* handle consumer commission setter/getter gracefully to avoid BeginBlock panic + add msg in codec

* fix consumer commission query rest path

* fix: update queries REST path for PSS (#1839)

update queries rest path

* Clarify that GetProposedConsumerChain is test-only

* fix: Fix has-to-validate query (#1823)

* Fix has-to-validate query

* Flip comparison sign for checking minPower

* Regenerate traces

* Remove unnecessary print

* Address comments

* fix!: fix slashing in PSS (#1838)

* drop slash packet for opted-out validators before updating slash meter

* fix integration test

* fix ut

* update UT

* Update x/ccv/provider/types/msg.go

Co-authored-by: Marius Poke <[email protected]>

* Remove BlockValidatorUpdate from expected staking keeper

* added an error response value to ComputeMinPowerToOptIn

* delete additional state when we stop a chain

* Assign keys and change voting power only for unjailed nodes with >0 power

* fix: Validate consumer commission rate against minimal rate (#1834)

* Validate consumer commission rate

* Add test for commission rates

* Remove static minimum commission rate validation from Set

* feat!: introduce power shaping (#1830)

* added power shaping

* fixes

* Add property based test for power cap

* fixed tests & added algorithm's idea

* nit changes

* Update x/ccv/provider/keeper/proposal.go

Co-authored-by: Philip Offtermatt <[email protected]>

* remove empty-validator-set check

* implicit memory aliasing issue fixed

* added keeper tests

* updated HasToValidate query

* Update x/ccv/provider/keeper/keeper.go

Co-authored-by: Philip Offtermatt <[email protected]>

* Update x/ccv/provider/keeper/keeper.go

Co-authored-by: Philip Offtermatt <[email protected]>

* took into account comments

* do not use cached ctx

* Fix E2E test. A jailed validator does not have to validate.

* fix merge issue and format

---------

Co-authored-by: Philip Offtermatt <[email protected]>
Co-authored-by: Philip Offtermatt <[email protected]>

* Update v4 to v5 in package version

* Bump consensus version

* Add migration in correct folder

* Update version from v4 to v5 in migration

---------

Co-authored-by: mpoke <[email protected]>
Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: insumity <[email protected]>
Co-authored-by: insumity <[email protected]>
Co-authored-by: Simon Noetzlin <[email protected]>

* chore: add v5.0.x-provider and v5.0.x-provider to mergify and dependabot (#1845)

updated bots for v5.0.x-provider release

* fix: revert version bump to v5 (#1847)

* revert bump version to 5

* register migration

* chore: rm v5-provider; add v4.2.0; rm old versions (#1849)

* chore: rm v5-provider; add v4.2.0; rm old versions

* chore: rm v5-provider; add v4.2.0; rm old versions

* chore: Add coderabbit configuration file (#1852)

* Add coderabbit configuration file

* Add release and feat base branches to coderabbit

* Change config to not auto-post review status on unreviewed PRs

* refactor: remove redundant code from MakeConsumerGenesis (#1807)

* remove redundant code from MakeConsumerGenesis

* fix tests

* refactor: nit naming changes (#1854)

* small naming fix

* reverts name to ComputeNextValidators because the semantics of ComputeNextEpochConsumerValSet were different in v4.1

* docs: ADR for Security Aggregation solution (#1866)

* ADR CosmoLayer: Initial draft

* update adr: slinky api

* cleanup

* Apply suggestions from code review

Co-authored-by: Marius Poke <[email protected]>

* addressed comments

* cleanup of pseudo code, power sources

* renaming to security aggregation

* mv adr

* removed comments

* minor change in code example

* Apply suggestions from code review

Grammar

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

---------

Co-authored-by: Marius Poke <[email protected]>
Co-authored-by: Jehan <[email protected]>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* chore: Make coderabbit ignore docs folder (#1864)

Make bot ignore docs folder

* chore: Fix codespell config (#1869)

* Add optin and opt-in to codespell ignored words

* Fix typo on multiple

* Fix typo on assignment

* feat: PSS - Add minimum power in top N & power shaping params to consumer chain list (#1863)

* Add minimum power in top N to the list-consumer-chains query

* Add test for MinPowerInTop_N

* Add changelog entry

* Update x/ccv/provider/keeper/keeper_test.go

Co-authored-by: insumity <[email protected]>

* Add other validator shaping params to consumer chain list

* Add power shaping params to query test

* Adjust changelog for extra fields

* Add changelog entry for API breaking

---------

Co-authored-by: insumity <[email protected]>

* chore: fixed all-pairs-valconsensus-address CLI command usage (#1870)

* chore: Try to make coderabbit ignore missing/extra newlines in md files (#1877)

Update .coderabbit.yml

* docs: Add PSS docs (#1859)

* Add params to proposals

* Start rewriting intro

* Finish overview and terminology

* Write up generics about PSS and power shaping

* Add more info about top N and optin

* Nit: apostrophe

* Clarify governance proposal process for Opt In chains

* Apply suggestions from code review

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* Add missing newlines

* Update docs/docs/features/partial-set-security.md

Co-authored-by: insumity <[email protected]>

* Update docs/docs/features/power-shaping.md

Co-authored-by: insumity <[email protected]>

* Use Interchain Security instead of ICSv2

* docs: Add PSS docs (Part 2) (#1861)

* first version

* first commit

* one more warning on having all validators opt out

* Update docs/docs/validators/partial-set-security-for-validators.md

Co-authored-by: Philip Offtermatt <[email protected]>

* Update docs/docs/validators/partial-set-security-for-validators.md

Co-authored-by: Philip Offtermatt <[email protected]>

* Update docs/docs/validators/partial-set-security-for-validators.md

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* Update docs/docs/validators/partial-set-security-for-validators.md

Co-authored-by: Philip Offtermatt <[email protected]>

* Update docs/docs/frequently-asked-questions.md

Co-authored-by: Philip Offtermatt <[email protected]>

* Update docs/docs/validators/partial-set-security-for-validators.md

Co-authored-by: Philip Offtermatt <[email protected]>

* Update docs/docs/frequently-asked-questions.md

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* Update docs/docs/validators/partial-set-security-for-validators.md

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* took into account some comments

* small comment changes

---------

Co-authored-by: Philip Offtermatt <[email protected]>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* Add warning that vals have to manually opt out if going out of top N

* Add short PSS FAQ

* Add FAQ on how many chains vals can opt in on

* Change first to third person

* Fix typo

* Add missing comma

* added a warning

* Add more guidelines to 'how to choose the power shaping parameters'

* Mention list-consumer-chains query

* Add tip about default commission rate

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>
Co-authored-by: insumity <[email protected]>

* docs: Minor improvements (#1882)

* Fix typo in tip

* Minor improvements around commission rate

* Mention soft opt-out

* Link to normal consumer addition prop

* Remove confusing line from changeover prop

* Remove instructions about not assigning keys

* Clarify starting condition for top N chains

* Incorporate comments

* Update docs/docs/validators/joining-testnet.md

Co-authored-by: insumity <[email protected]>

* Reformulate opting out

---------

Co-authored-by: insumity <[email protected]>

* build(deps): bump google.golang.org/protobuf from 1.33.0 to 1.34.1 (#1862)

Bumps google.golang.org/protobuf from 1.33.0 to 1.34.1.

---
updated-dependencies:
- dependency-name: google.golang.org/protobuf
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* feat: add a query to retrieve validator set that was last sent to the consumer chain (#1867)

* init commit

* took into account comments

* add docs

* Update docs/docs/validators/partial-set-security-for-validators.md

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* fix!: drop chain proposals with empty validator set at spawn time (#1888)

* init commit

* Update x/ccv/provider/keeper/proposal.go

Co-authored-by: MSalopek <[email protected]>

* added one more test case

---------

Co-authored-by: MSalopek <[email protected]>

* test: Remove v5.0.0 (pre-release) be tested within e2e compatibility (#1894)

* Remove v5.0.0 (pre-release) from last version to be tested within e2e comopatibility tests

* Apply suggestions from code review

Co-authored-by: Marius Poke <[email protected]>

---------

Co-authored-by: Marius Poke <[email protected]>

* test: add E2E test for power-shaping features (#1853)

* added E2E tests

* Update tests/e2e/steps_partial_set_security.go

Co-authored-by: Philip Offtermatt <[email protected]>

* added to nightly tests

---------

Co-authored-by: Philip Offtermatt <[email protected]>

* build(deps): bump comet to v0.37.6 (#1876)

* bump comet to v0.37.6

* add changelog entry

* fix exp deps and pin it to go.mod

* bump comet to 0.37.5 and sdk to 0.47.11 to match

* bump comet back to 0.37.6

* add changelog entry for SDK

---------

Co-authored-by: MSalopek <[email protected]>

* docs: add v4.2.0; bump v5.0.0 (#1900)

* docs: add v4.2.0; bump v5.0.0

* docs: add v4.2.0; bump v5.0.0

* docs: fix broken docs deploy (v4.2.0) (#1903)

* docs: add v4.2.0; bump v5.0.0

* docs: add v4.2.0; bump v5.0.0

* sync

* sync stuff

* fix

* try docs tag

* add version alias

* chore: fix spelling errors (#1904)

chore: spelling errors fixes

Co-authored-by: github-merge-queue <[email protected]>

* build(deps): bump JamesIves/github-pages-deploy-action from 4.6.0 to 4.6.1 (#1905)

build(deps): bump JamesIves/github-pages-deploy-action

Bumps [JamesIves/github-pages-deploy-action](https://github.com/jamesives/github-pages-deploy-action) from 4.6.0 to 4.6.1.
- [Release notes](https://github.com/jamesives/github-pages-deploy-action/releases)
- [Commits](https://github.com/jamesives/github-pages-deploy-action/compare/v4.6.0...v4.6.1)

---
updated-dependencies:
- dependency-name: JamesIves/github-pages-deploy-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump bufbuild/buf-setup-action from 1.31.0 to 1.32.0 (#1906)

Bumps [bufbuild/buf-setup-action](https://github.com/bufbuild/buf-setup-action) from 1.31.0 to 1.32.0.
- [Release notes](https://github.com/bufbuild/buf-setup-action/releases)
- [Commits](https://github.com/bufbuild/buf-setup-action/compare/v1.31.0...v1.32.0)

---
updated-dependencies:
- dependency-name: bufbuild/buf-setup-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump google.golang.org/grpc from 1.63.2 to 1.64.0 (#1908)

Bumps [google.golang.org/grpc](https://github.com/grpc/grpc-go) from 1.63.2 to 1.64.0.
- [Release notes](https://github.com/grpc/grpc-go/releases)
- [Commits](https://github.com/grpc/grpc-go/compare/v1.63.2...v1.64.0)

---
updated-dependencies:
- dependency-name: google.golang.org/grpc
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* docs: document democracy modules in more detail (#1915)

* docs: document democracy modules in more detail

* docs: add diff to config

* Update docs/docs/features/democracy-modules.md

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* Update docs/docs/features/democracy-modules.md

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* Update docs/docs/features/democracy-modules.md

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* cleanup after applying bot comments

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* docs: bring v4.2.0 changelog to main (#1909)

bring v4.2.0 changelog to main

* build(deps): bump github.com/cosmos/ibc-go/v7 from 7.4.0 to 7.5.0 (#1907)

* build(deps): bump github.com/cosmos/ibc-go/v7 from 7.4.0 to 7.5.0

Bumps [github.com/cosmos/ibc-go/v7](https://github.com/cosmos/ibc-go) from 7.4.0 to 7.5.0.
- [Release notes](https://github.com/cosmos/ibc-go/releases)
- [Changelog](https://github.com/cosmos/ibc-go/blob/main/CHANGELOG.md)
- [Commits](https://github.com/cosmos/ibc-go/compare/v7.4.0...v7.5.0)

---
updated-dependencies:
- dependency-name: github.com/cosmos/ibc-go/v7
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>

* add changelong entry

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: mpoke <[email protected]>

* chore: fix spelling errors (#1922)

chore: spelling errors fixes

Co-authored-by: github-merge-queue <[email protected]>

* fix(client): write unbonding period advisory to stderr instead of stdout (#1921)

* fix(client): write unbonding period advisory to stderr instead of stdout

* Add changelog for unbonding period advisory

---------

Co-authored-by: Philip Offtermatt <[email protected]>

* docs: update ADR metadata (#1910)

* update ADR metadata

* fix broken link

* build(deps): bump github.com/cosmos/ibc-go/v7 from 7.5.0 to 7.5.1 (#1924)

* build(deps): bump github.com/cosmos/ibc-go/v7 from 7.5.0 to 7.5.1

Bumps [github.com/cosmos/ibc-go/v7](https://github.com/cosmos/ibc-go) from 7.5.0 to 7.5.1.
- [Release notes](https://github.com/cosmos/ibc-go/releases)
- [Changelog](https://github.com/cosmos/ibc-go/blob/v7.5.1/CHANGELOG.md)
- [Commits](https://github.com/cosmos/ibc-go/compare/v7.5.0...v7.5.1)

---
updated-dependencies:
- dependency-name: github.com/cosmos/ibc-go/v7
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

* update changelog entry

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: mpoke <[email protected]>

* build(deps): bump bufbuild/buf-setup-action from 1.32.0 to 1.32.1 (#1923)

Bumps [bufbuild/buf-setup-action](https://github.com/bufbuild/buf-setup-action) from 1.32.0 to 1.32.1.
- [Release notes](https://github.com/bufbuild/buf-setup-action/releases)
- [Commits](https://github.com/bufbuild/buf-setup-action/compare/v1.32.0...v1.32.1)

---
updated-dependencies:
- dependency-name: bufbuild/buf-setup-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump bufbuild/buf-setup-action from 1.32.1 to 1.32.2 (#1934)

Bumps [bufbuild/buf-setup-action](https://github.com/bufbuild/buf-setup-action) from 1.32.1 to 1.32.2.
- [Release notes](https://github.com/bufbuild/buf-setup-action/releases)
- [Commits](https://github.com/bufbuild/buf-setup-action/compare/v1.32.1...v1.32.2)

---
updated-dependencies:
- dependency-name: bufbuild/buf-setup-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump github.com/spf13/viper from 1.18.2 to 1.19.0 (#1936)

Bumps [github.com/spf13/viper](https://github.com/spf13/viper) from 1.18.2 to 1.19.0.
- [Release notes](https://github.com/spf13/viper/releases)
- [Commits](https://github.com/spf13/viper/compare/v1.18.2...v1.19.0)

---
updated-dependencies:
- dependency-name: github.com/spf13/viper
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump docker/login-action from 3.1.0 to 3.2.0 (#1935)

Bumps [docker/login-action](https://github.com/docker/login-action) from 3.1.0 to 3.2.0.
- [Release notes](https://github.com/docker/login-action/releases)
- [Commits](https://github.com/docker/login-action/compare/e92390c5fb421da1463c202d546fed0ec5c39f20...0d4c9c5ea7693da7b068278f7b52bda2a190a446)

---
updated-dependencies:
- dependency-name: docker/login-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* docs: Add draft ADR for validators outside of the active set (#1879)

* Add draft ADR for active set validators

* Remove unused changelog entry

* Add initial date and remove square brackets

* Suggest alternative approach: unbonded validators can validate

* Expand unbonded validators section a bit

* Incorporate comments

* Update docs/docs/adrs/adr-017-allowing-inactive-validators.md

Co-authored-by: Marius Poke <[email protected]>

* Update docs/docs/adrs/adr-017-allowing-inactive-validators.md

Co-authored-by: Marius Poke <[email protected]>

* Update docs/docs/adrs/adr-017-allowing-inactive-validators.md

Co-authored-by: Marius Poke <[email protected]>

* Clarify consensus validators vs staking validators

* Update ADR to roll context doc into it

* Fix image links

* Add negative consequence

* Add sentence about module wiring

* Address review comments

* Add source code for diagrams and make text more technical

* Update docs/docs/adrs/adr-017-allowing-inactive-validators.md

Co-authored-by: Marius Poke <[email protected]>

* Update docs/docs/adrs/adr-017-allowing-inactive-validators.md

Co-authored-by: Marius Poke <[email protected]>

* Update docs/docs/adrs/adr-017-allowing-inactive-validators.md

Co-authored-by: Jehan <[email protected]>

* Write changes to state

* Update intro, links, mitigations

---------

Co-authored-by: Marius Poke <[email protected]>
Co-authored-by: Jehan <[email protected]>

* chore: fix struct name in comment (#1938)

Signed-off-by: xiaoxiangirl <[email protected]>

* feat!: allow consumer chains to change their PSS parameters (#1932)

* added modification proposal

* small fixes

* Update x/ccv/provider/client/proposal_handler.go

Co-authored-by: Philip Offtermatt <[email protected]>

* removed trailing comma

* Update x/ccv/provider/types/proposal.go

Co-authored-by: Philip Offtermatt <[email protected]>

* Update x/ccv/provider/types/proposal.go

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* took into account comment

---------

Co-authored-by: Philip Offtermatt <[email protected]>
Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* fix!: apply audit suggestions (#1925)

* init commit

* added CHANGELOG entries

* added nit simplification change

* addressed comment by Hypha

* took into account err returned by ComputeMinPowerToOptIn

* fixed test failing

* build(deps): bump github.com/cosmos/ibc-go/v7 from 7.5.0 to 7.5.1 (#1924)

* build(deps): bump github.com/cosmos/ibc-go/v7 from 7.5.0 to 7.5.1

Bumps [github.com/cosmos/ibc-go/v7](https://github.com/cosmos/ibc-go) from 7.5.0 to 7.5.1.
- [Release notes](https://github.com/cosmos/ibc-go/releases)
- [Changelog](https://github.com/cosmos/ibc-go/blob/v7.5.1/CHANGELOG.md)
- [Commits](https://github.com/cosmos/ibc-go/compare/v7.5.0...v7.5.1)

---
updated-dependencies:
- dependency-name: github.com/cosmos/ibc-go/v7
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>

* update changelog entry

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: mpoke <[email protected]>

* build(deps): bump bufbuild/buf-setup-action from 1.32.0 to 1.32.1 (#1923)

Bumps [bufbuild/buf-setup-action](https://github.com/bufbuild/buf-setup-action) from 1.32.0 to 1.32.1.
- [Release notes](https://github.com/bufbuild/buf-setup-action/releases)
- [Commits](https://github.com/bufbuild/buf-setup-action/compare/v1.32.0...v1.32.1)

---
updated-dependencies:
- dependency-name: bufbuild/buf-setup-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump bufbuild/buf-setup-action from 1.32.1 to 1.32.2 (#1934)

Bumps [bufbuild/buf-setup-action](https://github.com/bufbuild/buf-setup-action) from 1.32.1 to 1.32.2.
- [Release notes](https://github.com/bufbuild/buf-setup-action/releases)
- [Commits](https://github.com/bufbuild/buf-setup-action/compare/v1.32.1...v1.32.2)

---
updated-dependencies:
- dependency-name: bufbuild/buf-setup-action
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump github.com/spf13/viper from 1.18.2 to 1.19.0 (#1936)

Bumps [github.com/spf13/viper](https://github.com/spf13/viper) from 1.18.2 to 1.19.0.
- [Release notes](https://github.com/spf13/viper/releases)
- [Commits](https://github.com/spf13/viper/compare/v1.18.2...v1.19.0)

---
updated-dependencies:
- dependency-name: github.com/spf13/viper
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump docker/login-action from 3.1.0 to 3.2.0 (#1935)

Bumps [docker/login-action](https://github.com/docker/login-action) from 3.1.0 to 3.2.0.
- [Release notes](https://github.com/docker/login-action/releases)
- [Commits](https://github.com/docker/login-action/compare/e92390c5fb421da1463c202d546fed0ec5c39f20...0d4c9c5ea7693da7b068278f7b52bda2a190a446)

---
updated-dependencies:
- dependency-name: docker/login-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* took into account comments

---------

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>
Co-authored-by: mpoke <[email protected]>

* chore: fix spelling errors (#1939)

chore: spelling errors fixes

Co-authored-by: github-merge-queue <[email protected]>

* fix!: Replace GetAllConsumerChains with lightweight version (#1946)

* add GetAllConsumerChainIDs

* replace GetAllConsumerChains with GetAllRegisteredConsumerChainIDs

* add changelog entry

* move HasToValidate to grpc_query.go as it's used only there

* apply review suggestions

* feat!: added E2E test and docs for ConsumerModificationProposal (#1949)

* added E2E test for the ConsumerModificationProposal

* added docs

* add to nightly tests

* fix markdown links

* Update docs/docs/features/proposals.md

Co-authored-by: Philip Offtermatt <[email protected]>

---------

Co-authored-by: Philip Offtermatt <[email protected]>

* build(deps): bump golang.org/x/mod from 0.17.0 to 0.18.0 (#1955)

Bumps [golang.org/x/mod](https://github.com/golang/mod) from 0.17.0 to 0.18.0.
- [Commits](https://github.com/golang/mod/compare/v0.17.0...v0.18.0)

---
updated-dependencies:
- dependency-name: golang.org/x/mod
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* chore: add last PSS changes to changelog (#1944)

add last PSS changes to changelog

* test: Add integration test reproducing the LastValidators exceeding MaxValidators bug (#1945)

* Add test reproducing the LastValidators exceeding MaxValidators

* formatting

* Update tests/integration/unbonding.go

Co-authored-by: insumity <[email protected]>

* Update tests/integration/unbonding.go

Co-authored-by: Philip Offtermatt <[email protected]>

* document

---------

Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Co-authored-by: insumity <[email protected]>
Co-authored-by: Philip Offtermatt <[email protected]>

* test: Add an e2e test that reproduces the chain halt (#1942)

* Start writing e2e test with unjailing

* Add e2e steps for too many validators bug

* Fix test config and setup

* Change test to use top N chain

* Add comment for panic

* Start cleaning up active/inactive vals e2e test

* Revert change to StartChains

* Revert changes to partial-set-security tests

* Rename test case

* Rename CLI flag for test case

* Address comments

* Add active set changes test to nightly runs

* Fix merge in main.go

* docs: update releases (bots and docs) (#1948)

* update bots

* update releases and features

* build(deps): bump docker/build-push-action from 5.3.0 to 5.4.0 (#1954)

Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 5.3.0 to 5.4.0.
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](https://github.com/docker/build-push-action/compare/2cdde995de11925a030ce8070c3d77a52ffcf1c0...ca052bb54ab0790a636c9b5f226502c73d547a25)

---
updated-dependencies:
- dependency-name: docker/build-push-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* refactor: use IterateLastValidatorPowers instead of GetLastValidators (#1953)

* Add skeleton for GetLastValidators wrapper

* Fix unit tests

* Correct comment

* Log error messages if validators are not found

* Change AnyTimes to more specific Times(1)

* Instantiate slices with their max length and truncate

* Remove GetLastValidators from expectation

* Remove GetLastValidators call in consumer

* Move GetLastBondedValidators to validator_set_updates

* Add comment on iteration loop

* ci: fix merge issue on nightly e2e workflow (#1959)

* fix merge issue on nightly e2e

* addressed comments

* feat!: store the minimal power to be in the top N on EndBlock, instead of computing on-the-fly (#1952)

* Store the minimal power among the top N in EndBlock

* Finish merge

* Fix unit tests

* Fix store method for the min power

* Fix migration

* Revert migration changes

* Change comment to proper name for key

* Add staking keeper to migration

* Revert "Add staking keeper to migration"

This reverts commit 575cfd3ccec7732e0d1488d80bda7f6172110cf7.

* Rename migration

* Update x/ccv/provider/keeper/grpc_query.go

* Clean up minimal power in top N on StopConsumerChain

* Set min power in consumer modification proposal

* Address comments

* Use GetLastBondedValidators instead of GetLastValidators

* Add migration

* Add comment for migration

* Improve comment in migration

* Handle case where topN is not found

* Add test for updating minimum power in top N

* Merged tests

* Rename updatedMinPower->newUpdatedMinPower

* Address comments

* fix: print test name instead of config name (#1961)

* Fix: print test name instead of config name

* Add the config back in the report

* chore: add ICS `release/v5.1.x` branch to Mergify (#1962)

add release/v5.1.x brancg to mergify

* build(deps): bump google.golang.org/protobuf from 1.34.1 to 1.34.2 (#1958)

Bumps google.golang.org/protobuf from 1.34.1 to 1.34.2.

---
updated-dependencies:
- dependency-name: google.golang.org/protobuf
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* feat!: only distribute rewards to validators that have been validating a consumer chain for some time (#1929)

* init commit

* added a warning

* took into account comments

* init commit

* added a warning

* took into account comments

* added a comment

* Update .changelog/unreleased/improvements/provider/1929-distribute-rewards-to-long-term-validating-validators.md

Co-authored-by: Marius Poke <[email protected]>

* Update .changelog/unreleased/state-breaking/provider/1929-distribute-rewards-to-long-term-validating-validators.md

Co-authored-by: Marius Poke <[email protected]>

* took into account comments

---------

Co-authored-by: Marius Poke <[email protected]>

* chore: add bots for v4.3.0 (#1975)

add bots for v4.3.0

* chore: bump ibc-go to v7.6.0 (#1974)

* deps!: bump ibc-go to v7.6.0

* docs: update changelog files

* docs: add docs section to RELEASE_PROCESS.md (#1976)

* docs: add docs section to RELEASE_PROCESS.md

* docs: update the release notes template

* docs: bring v4.3.0 changelog to main (#1980)

* bring v4.3.0 changelog to main

* fix release notes template

* build(deps): bump github.com/spf13/cobra from 1.8.0 to 1.8.1 (#1967)

Bumps [github.com/spf13/cobra](https://github.com/spf13/cobra) from 1.8.0 to 1.8.1.
- [Release notes](https://github.com/spf13/cobra/releases)
- [Commits](https://github.com/spf13/cobra/compare/v1.8.0...v1.8.1)

---
updated-dependencies:
- dependency-name: github.com/spf13/cobra
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump bufbuild/buf-setup-action from 1.32.2 to 1.33.0 (#1968)

Bumps [bufbuild/buf-setup-action](https://github.com/bufbuild/buf-setup-action) from 1.32.2 to 1.33.0.
- [Release notes](https://github.com/bufbuild/buf-setup-action/releases)
- [Commits](https://github.com/bufbuild/buf-setup-action/compare/v1.32.2...v1.33.0)

---
updated-dependencies:
- dependency-name: bufbuild/buf-setup-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump docker/build-push-action from 5.4.0 to 6.0.0 (#1969)

Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 5.4.0 to 6.0.0.
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](https://github.com/docker/build-push-action/compare/ca052bb54ab0790a636c9b5f226502c73d547a25...c382f710d39a5bb4e430307530a720f50c2d3318)

---
updated-dependencies:
- dependency-name: docker/build-push-action
  dependency-type: direct:production
  update-type: version-update:semver-major
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* docs: mention PSS in changeover procedure and replace Replicated Security with Interchain Security (#1981)

* removed sentence that stated that "no opt-in mechanism available"

* changed replicated security to interchain security

* added PSS info box in the changeover procedure

* chore: fix typos (#1973)

* fix typos

* fix typo

* fix typos

* fix typos

* fix typo

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

---------

Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com>

* docs: update ADRs rendering (#1937)

* update ADRs in docs

* chore: ignore templates directories in docs folder

* fix broken links

* fix broken links

---------

Co-authored-by: MSalopek <[email protected]>

* refactor!: deprecate soft opt-out (#1964)

* first commit

* Set soft_opt_out_threshold to 0 instead of empty

* added changelog

* Update docs/docs/adrs/adr-009-soft-opt-out.md

Co-authored-by: Philip Offtermatt <[email protected]>

* Update proto/interchain_security/ccv/v1/shared_consumer.proto

Co-authored-by: Philip Offtermatt <[email protected]>

* Update .changelog/unreleased/improvements/consumer/1964-deprecate-soft-opt-out.md

Co-authored-by: Marius Poke <[email protected]>

* fixed changelogs

* added changelogs

* nit fix

* added changelog in ADR

* took into account comments.

* small fix

* fixed small issue

---------

Co-authored-by: Philip Offtermatt <[email protected]>
Co-authored-by: Marius Poke <[email protected]>

* build(deps): bump docker/build-push-action from 6.0.0 to 6.1.0 (#1989)

Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 6.0.0 to 6.1.0.
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](https://github.com/docker/build-push-action/compare/c382f710d39a5bb4e430307530a720f50c2d3318...31159d49c0d4756269a0940a750801a1ea5d7003)

---
updated-dependencies:
- dependency-name: docker/build-push-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump bufbuild/buf-setup-action from 1.33.0 to 1.34.0 (#1988)

Bumps [bufbuild/buf-setup-action](https://github.com/bufbuild/buf-setup-action) from 1.33.0 to 1.34.0.
- [Release notes](https://github.com/bufbuild/buf-setup-action/releases)
- [Commits](https://github.com/bufbuild/buf-setup-action/compare/v1.33.0...v1.34.0)

---
updated-dependencies:
- dependency-name: bufbuild/buf-setup-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump github.com/hashicorp/go-getter from 1.7.4 to 1.7.5 (#1994)

Bumps [github.com/hashicorp/go-getter](https://github.com/hashicorp/go-getter) from 1.7.4 to 1.7.5.
- [Release notes](https://github.com/hashicorp/go-getter/releases)
- [Changelog](https://github.com/hashicorp/go-getter/blob/main/.goreleaser.yml)
- [Commits](https://github.com/hashicorp/go-getter/compare/v1.7.4...v1.7.5)

---
updated-dependencies:
- dependency-name: github.com/hashicorp/go-getter
  dependency-type: indirect
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* chore: fix comment (#1972)

Signed-off-by: rustco <[email protected]>

* build(deps): bump docker/build-push-action from 6.1.0 to 6.2.0 (#2003)

Bumps [docker/build-push-action](https://github.com/docker/build-push-action) from 6.1.0 to 6.2.0.
- [Release notes](https://github.com/docker/build-push-action/releases)
- [Commits](https://github.com/docker/build-push-action/compare/31159d49c0d4756269a0940a750801a1ea5d7003...15560696de535e4014efeff63c48f16952e52dd1)

---
updated-dependencies:
- dependency-name: docker/build-push-action
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <[email protected]>
Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com>

* build(deps): bump amannn/action-semantic-pull-request from 5.5.2 to 5.5.3 (#2002)

build(deps): bump amannn/action-semantic-pull-request

Bumps [amannn/action-semantic-pull-request](https://github.com/amannn/action-semantic-pull-r…
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A:backport/v4.0.x C:ADR Assigned automatically by the PR labeler C:Docs Assigned automatically by the PR labeler
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Docs]: Interchain Security Docs - Changeover Procedure
3 participants